v0.8.10

Compare Source

compare changes

🩹 Fixes

• vectorize: Return undefined instead of throwing in dev with no remote (#​399)

❤️ Contributors

• Sébastien Chopin (@​atinux)

v0.8.9

Compare Source

compare changes

🩹 Fixes

• blob: Handle pdf type correctly in ensureBlob (#​392)
• migration: Invalid behavior while using -- or /* */ inside column string (#​397)
• Register vectorize utils even if not running remotely (#​396)

📖 Documentation

• blob: Proper input file type specifiers (#​393)
• Improve postgres hyperdrive binding example (#​394)

🏡 Chore

• Update deps (f420340)

❤️ Contributors

• Sébastien Chopin [email protected]
• Daniel Roe (@​danielroe)
• Farnabaz [email protected]
• Gerben Mulder <github.undergo381@​passmail.net>
• Yizack Rangel (@​Yizack)

v1.2.0

Compare Source

compare changes

🚀 Enhancements

• Expose genObjectKey and wrapInDelimiters utils (227ec06)

📖 Documentation

• Correct jsdocs for genObjectFromRaw (#​97)

🏡 Chore

• Update deps (02a2f68)
• Update eslint (c58341b)
• Apply automated updates (63cd869)

❤️ Contributors

• Pooya Parsa (@​pi0)

v3.99.0

Compare Source

Minor Changes

• #​7425 8757579 Thanks @​CarmenPopoviciu! - feat: Make DX improvements in wrangler dev --remote

  Workers + Assets projects have, in certain situations, a relatively degraded wrangler dev --remote developer experience, as opposed to Workers proper projects. This is due to the fact that, for Workers + Assets, we need to make extra API calls to:

  1. check for asset files changes
  2. upload the changed assets, if any

  This commit improves the wrangler dev --remote DX for Workers + Assets, for use cases when the User Worker/assets change while the API calls for previous changes are still in flight. For such use cases, we have put an exit early strategy in place, that drops the event handler execution of the previous changes, in favour of the handler triggered by the new changes.

• #​7537 086a6b8 Thanks @​WillTaylorDev! - Provide validation around assets.experimental_serve_directly

• #​7568 2bbcb93 Thanks @​WillTaylorDev! - Warn users when using smart placement with Workers + Assets and serve_directly is set to false

Patch Changes

• #​7521 48e7e10 Thanks @​emily-shen! - feat: add experimental_patchConfig()

  experimental_patchConfig() can add to a user's config file. It preserves comments if its a wrangler.jsonc. However, it is not suitable for wrangler.toml with comments as we cannot preserve comments on write.

• Updated dependencies [1488e11, 7216835]:

  • [email protected]

v3.98.0

Compare Source

Minor Changes

• #​7476 5124b5d Thanks @​WalshyDev! - feat: allow routing to Workers with Assets on any HTTP route, not just the root. For example, example.com/blog/* can now be used to serve assets.
  These assets will be served as though the assets directly were mounted to the root.
  For example, if you have assets = { directory = "./public/" }, a route like "example.com/blog/*" and a file ./public/blog/logo.png, this will be available at example.com/blog/logo.png. Assets outside of directories which match the configured HTTP routes can still be accessed with the Assets binding or with a Service binding to this Worker.

• #​7380 72935f9 Thanks @​CarmenPopoviciu! - Add Workers + Assets support in wrangler dev --remote

Patch Changes

• #​7573 fb819f9 Thanks @​emily-shen! - feat: add experimental_readRawConfig()

  Adds a Wrangler API to find and read a config file

• #​7549 42b9429 Thanks @​penalosa! - Expand metrics collection to:

  • Detect Pages & Workers CI
  • Filter out default args (e.g. --x-versions, --x-dev-env, and --latest) by only including args that were in argv

• #​7583 8def8c9 Thanks @​penalosa! - Revert support for custom unenv resolve path to address an issue with Wrangler failing to deploy Pages projects with nodejs_compat_v2 in some cases

v3.97.0

Compare Source

Minor Changes

• #​7522 6403e41 Thanks @​vicb! - feat(wrangler): allow overriding the unenv preset.

  By default wrangler uses the bundled unenv preset.

  Setting WRANGLER_UNENV_RESOLVE_PATHS allow to use another version of the preset.
  Those paths are used when resolving the unenv module identifiers to absolute paths.
  This can be used to test a development version.

• #​7479 2780849 Thanks @​penalosa! - Accept a JSON file of the format { name: string }[] in wrangler kv bulk delete, as well as the current string[] format.

Patch Changes

• #​7541 ca9410a Thanks @​vicb! - chore(wrangler): update unenv dependency version

• #​7345 15aa936 Thanks @​edmundhung! - fix(wrangler): keypress event name is optional

v3.96.0

Compare Source

Minor Changes

• #​7510 004af53 Thanks @​oliy! - Add file prefix option to wrangler pipelines commands

• #​7383 8af3365 Thanks @​jonesphillip! - Added wrangler r2 domain get command

Patch Changes

• #​7542 f13c897 Thanks @​CarmenPopoviciu! - Always print deployment and placement ID in Cloudchamber commands

  Currently, Cloudchamber commands only print the full deployment ID when the deployment has an IPv4 address. This commit ensures the deployment ID and the placement ID are always printed to stdout. It also moves the printing of the IPv4 address (if one exists) to the same place as the IPv6 address so that they are printed together.

• #​6754 0356d0a Thanks @​bluwy! - refactor: move @cloudflare/workers-shared as dev dependency

• #​7478 2e90efc Thanks @​petebacondarwin! - fix: ensure that non-inherited fields are not removed when using an inferred named environment

  It is an error for the the user to provide an environment name that doesn't match any of the named environments in the Wrangler configuration.
  But if there are no named environments defined at all in the Wrangler configuration, we special case the top-level environment as though it was a named environment.
  Previously, when this happens, we would remove all the nonInheritable fields from the configuration (essentially all the bindings) leaving an incorrect configuration.
  Now we correctly generate a flattened named environment that has the nonInheritable fields, plus correctly applies any transformFn on inheritable fields.

• #​7524 11f95f7 Thanks @​gpanders! - Include response body in Cloudchamber API errors

• #​7427 3bc0f28 Thanks @​edmundhung! - The x-provision experimental flag now identifies draft and inherit bindings by looking up the current binding settings.

  Draft bindings can then be provisioned (connected to new or existing KV, D1, or R2 resources) during wrangler deploy.

• Updated dependencies []:

  • [email protected]

v1.6.1

Compare Source

Bug Fixes

• lazy validation errors thrown in builders should resolve async like other validations (c7d7f97)

v1.6.0

Compare Source

Features

• expose LazySchema (2b0f126)